#!/bin/bash
# Description: Check latest version and security advisories for livekit-server-sdk

# Check NPM for latest versions
echo "Latest version from NPM:"
curl -s https://registry.npmjs.org/livekit-server-sdk | jq -r '."dist-tags".latest'

# Check for security advisories
echo -e "\nSecurity advisories from GitHub:"
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "livekit-server-sdk") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

#!/bin/bash
# Description: Verify the existence and exports of the LiveKit app module
# Expected: Find the app module and its listRooms method

# Check if the file exists and show its exports
fd -t f "livekit.app.mjs" -x cat {}

# Look for the listRooms method definition
ast-grep --pattern 'listRooms() {
  $$$
}'

#!/bin/bash
# Description: Verify the LiveKit app instance exports and deleteRoom method implementation

# Check for the app instance exports
ast-grep --pattern 'export $_ app = $_' components/livekit/livekit.app.mjs

# Check for deleteRoom method implementation
ast-grep --pattern 'deleteRoom($_) {
  $$$
}' components/livekit/livekit.app.mjs

#!/bin/bash
# Let's try a different approach to verify the app instance and its methods

# First, let's check if the file exists and see its content
fd "livekit.app.mjs" --type f

# If found, let's examine its content
rg -l "deleteRoom" --type js

# Let's also check for any LiveKit related files that might contain the implementation
fd "livekit" --type f

# Look for deleteRoom implementation across all files
rg "deleteRoom" -A 5 --type js

#!/bin/bash
# Let's examine the content of livekit.app.mjs since we confirmed it exists
cat components/livekit/livekit.app.mjs

# Also check the delete-room.mjs to understand how deleteRoom is being used
cat components/livekit/actions/delete-room/delete-room.mjs

#!/bin/bash
# Description: Check LiveKit app implementation and error handling patterns

# Check createRoom implementation
echo "Checking createRoom implementation..."
rg -A 10 "createRoom.*\{" components/livekit/

# Check error handling patterns across LiveKit actions
echo "Checking error handling patterns..."
rg -A 5 "try.*\{" components/livekit/actions/
rg -A 5 "catch.*\{" components/livekit/actions/

#!/bin/bash
# Let's check for error handling patterns more thoroughly

# Check for try-catch blocks in LiveKit actions
echo "Checking error handling in LiveKit actions..."
rg -B 2 -A 10 "export default" components/livekit/actions/create-room/create-room.mjs

# Check if there are consistent error handling patterns in other LiveKit actions
echo "Checking other LiveKit actions..."
fd . components/livekit/actions/ -t f -x cat {}

#!/bin/bash
# Let's check the LiveKit app implementation for error handling

# Check the app implementation
echo "Checking LiveKit app implementation..."
cat components/livekit/livekit.app.mjs

# Check for any common error handling utilities
echo "Checking for error utilities..."
fd . components/livekit/ -t f -x rg -l "try|catch|throw"

#!/bin/bash
# Description: Verify the parameter order of RoomServiceClient and IngressClient constructors in the livekit-server-sdk.

# Check the RoomServiceClient constructor
ast-grep --pattern $'class RoomServiceClient {
  constructor($_host, $_apiKey, $_secretKey, $$$) {
    $$$
  }
}'

# Check the IngressClient constructor
ast-grep --pattern $'class IngressClient {
  constructor($_host, $_apiKey, $_secretKey, $$$) {
    $$$
  }
}'

#!/bin/bash
# Let's try a different approach by searching for constructor patterns and imports
rg -U "constructor.*\(.*\)" --type js -A 5

# Also search for any imports or requires of these clients
rg "(import|require).*(?i)(RoomServiceClient|IngressClient)" --type js

#!/bin/bash
# Let's search for the actual usage of getKeys() to understand the client instantiation
rg -U "getKeys\(\)" --type js -A 5 -B 5

# Also search for any LiveKit related imports or client instantiation
rg "livekit" --type js -i

#!/bin/bash
# Let's check the file content directly to understand the client usage
cat components/livekit/livekit.app.mjs

# Also check for any LiveKit related files
fd -e js -e mjs -e ts livekit -i

#!/bin/bash
# Description: Search for LiveKit documentation references in the codebase
# Expected: Documentation links or comments referencing LiveKit's API

# Search for LiveKit documentation references
rg -i "livekit.*documentation|livekit.*api|livekit.*guide" .

# Search for TODO comments related to LiveKit
rg -i "todo.*livekit|fixme.*livekit" .

#!/bin/bash
# Let's verify the implementation against LiveKit's API usage patterns

# Check RoomServiceClient usage
ast-grep --pattern 'new RoomServiceClient($$$)'

# Check IngressClient usage
ast-grep --pattern 'new IngressClient($$$)'

# Check room-related method signatures
ast-grep --pattern 'createRoom($$$)'
ast-grep --pattern 'listRooms($$$)'
ast-grep --pattern 'deleteRoom($$$)'

# Check ingress-related method signatures
ast-grep --pattern 'createIngress($$$)'

#!/bin/bash
# Let's check the actual implementations in the action files referenced in documentation

# Check create-room implementation
cat ./components/livekit/actions/create-room/create-room.mjs

# Check list-rooms implementation
cat ./components/livekit/actions/list-rooms/list-rooms.mjs

# Check delete-room implementation
cat ./components/livekit/actions/delete-room/delete-room.mjs

# Check create-ingress implementation
cat ./components/livekit/actions/create-ingress-from-url/create-ingress-from-url.mjs